SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Volume (computing)</title>

</head>

<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Volume (computing)</span></span>

</h1>

</header>

/* start https://en.wikipedia.org/ */

.mw-parser-output .ambox{border:1px solid #a2a9b1;border-left:10px solid #36c;background-color:#fbfbfb;box-sizing:border-box}.mw-parser-output .ambox+link+.ambox,.mw-parser-output .ambox+link+style+.ambox,.mw-parser-output .ambox+link+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+style+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+link+.ambox{margin-top:-1px}html body.mediawiki .mw-parser-output .ambox.mbox-small-left{margin:4px 1em 4px 0;overflow:hidden;width:238px;border-collapse:collapse;font-size:88%;line-height:1.25em}.mw-parser-output .ambox-speedy{border-left:10px solid #b32424;background-color:#fee7e6}.mw-parser-output .ambox-delete{border-left:10px solid #b32424}.mw-parser-output .ambox-content{border-left:10px solid #f28500}.mw-parser-output .ambox-style{border-left:10px solid #fc3}.mw-parser-output .ambox-move{border-left:10px solid #9932cc}.mw-parser-output .ambox-protection{border-left:10px solid #a2a9b1}.mw-parser-output .ambox .mbox-text{border:none;padding:0.25em 0.5em;width:100%}.mw-parser-output .ambox .mbox-image{border:none;padding:2px 0 2px 0.5em;text-align:center}.mw-parser-output .ambox .mbox-imageright{border:none;padding:2px 0.5em 2px 0;text-align:center}.mw-parser-output .ambox .mbox-empty-cell{border:none;padding:0;width:1px}.mw-parser-output .ambox .mbox-image-div{width:52px}@media(min-width:720px){.mw-parser-output .ambox{margin:0 10%}}@media print{body.ns-0 .mw-parser-output .ambox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style>

<p>In computer data storage, a <b>volume</b> or <b>logical drive</b> is a single accessible storage area with a single <a href="File_system" title="File system">file system</a>, typically (though not necessarily) resident on a single <a href="Partition_(computing)" class="mw-redirect" title="Partition (computing)">partition</a> of a <a href="Hard_disk_drive" title="Hard disk drive">hard disk</a> (so-called <b>simple volume</b>). Although a volume might be different from a physical disk drive, it can still be accessed with an operating system's logical interface. However, a volume differs from a partition.

</p>

<div class="mw-heading mw-heading2"><h2 id="Differences_from_partition">Differences from partition</h2></div>

<p>A volume is not the same thing as a partition. For example, a <a href="Floppy_disk" title="Floppy disk">floppy disk</a> might be accessible as a volume, even though it does not contain a partition, as floppy disks cannot be partitioned with most modern computer software. Also, an OS can recognize a partition without recognizing any volume associated with it, as when the OS cannot interpret the filesystem stored there. This situation occurs, for example, when Windows NT-based OSes encounter disks with non-<a href="Microsoft" title="Microsoft">Microsoft</a> OS partitions, such as the <a href="Ext4" title="Ext4">ext4</a> filesystem commonly used with <a href="Linux" title="Linux">Linux</a>. Another example occurs in the <a href="Intel" title="Intel">Intel</a> world with the "Extended Partition". While these are partitions, they cannot contain a filesystem directly. Instead, "logical drives" (also known as volumes) must be created within them. This is also the case with NetWare volumes residing inside of a single partition. In short, volumes exist at the logical OS level, and partitions exist at the physical, media specific level. Sometimes there is a one-to-one correspondence, but this is not guaranteed.

</p><p>In Microsoft Windows Server 2008 and onward, the term "volume" is used as a superset that includes "partition" as well.<sup id="cite_ref-1" class="reference"><a href="#cite_note-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-2" class="reference"><a href="#cite_note-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-3" class="reference"><a href="#cite_note-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup>

</p><p>It isn't uncommon to see a volume packed into a single file. Examples include ISO9660 disc images (CD/DVD images, commonly called "ISOs"), and installer volumes for Mac OS X (<a href="Apple_Disk_Image" title="Apple Disk Image">DMGs</a>). As these volumes are files which reside within another volume, they certainly are <i>not</i> partitions.

</p>

<div class="mw-heading mw-heading3"><h3 id="Example">Example</h3></div>

<p>This example concerns a <a href="Windows_XP" title="Windows XP">Windows XP</a> system with two physical hard disks. The first hard disk has two partitions, the second has only one. The first partition of the first hard disk contains the operating system. <a href="Mount_point" class="mw-redirect" title="Mount point">Mount points</a> have been left at defaults.

</p>

<th>Physical disk</th>

<th>Partition</th>

<th>Filesystem</th>

<th>Drive letter

</th></tr>

<tr>

<td>Partition 1</td>

<td>C:

</td></tr>

<tr>

<td>Partition 2</td>

<td>D:

</td></tr>

<tr>

<td>Partition 1</td>

<td>E:

</td></tr></tbody></table>

<p>In this example,

</p>

<ul><li>"C:", "D:", and "E:" are volumes.</li>

<li>Hard Disk 1 and Hard Disk 2 are physical disks.</li>

<li>Any of these can be called a "drive".</li></ul>

<div class="mw-heading mw-heading2"><h2 id="Nomenclature">Nomenclature</h2></div>

<p>In <a href="Linux" title="Linux">Linux</a> systems, volumes are usually handled by the <a href="Logical_Volume_Manager" class="mw-redirect" title="Logical Volume Manager">Logical Volume Manager</a> or the <a href="Enterprise_Volume_Management_System" title="Enterprise Volume Management System">Enterprise Volume Management System</a> and manipulated using <a rel="nofollow" class="external text" href="http://www.netadmintools.com/html/8mount.man.html">mount(8)</a>. In <a href="Windows_NT" title="Windows NT">NT</a>-based versions of <a href="Microsoft_Windows" title="Microsoft Windows">Microsoft Windows</a>, volumes are handled by the kernel and managed using the Disk Management <a href="Microsoft_Management_Console" title="Microsoft Management Console">MMC snap-in</a> or the Diskpart command line tool.

</p>

<div class="mw-heading mw-heading3"><h3 id="Windows_NT-based_operating_systems">Windows NT-based operating systems</h3></div>

<p>Windows NT-based OSes do not have a single root <a href="Directory_(computing)" title="Directory (computing)">directory</a>. As a result, Windows will assign at least one path to each mounted volume, which will take one of two forms:

</p>

<ul><li>A <a href="Drive_letter" class="mw-redirect" title="Drive letter">drive letter</a>, in the form of a single letter followed by a <a href="Colon_(punctuation)" title="Colon (punctuation)">colon</a>, such as "F:"</li>

<li>A mount-point on an <a href="NTFS" title="NTFS">NTFS</a> volume having a drive letter, such as "<code>C:\Music</code>"</li></ul>

<p>In these two examples, a file called "Track 1.mp3" stored in the root directory of the mounted volume could be referred to as "<code>F:\Track 1.mp3</code>" or "<code>C:\Music\Track 1.mp3</code>", respectively.

</p><p>In order to assign a mount point for a volume as a path within another volume, the following criteria must be met:

</p>

<ul><li>The mounted-to volume must be formatted NTFS.</li>

<li>A directory must exist at the root path. (As of Windows Vista, it can be any subdirectory in a volume)</li>

<li>That directory must be empty.</li></ul>

<p>By default, Windows will assign drive letters to all drives, as follows:

</p>

<ul><li>"A:" and "B:" to floppy disk drives, whether present or not</li>

<li>"C:" and subsequent letters, as needed, to:

<ul><li>Hard disks</li>

<li>Removable disks, including optical media (e.g. CDs and DVDs)</li></ul></li></ul>

<p>Because of this <a href="Legacy_system" title="Legacy system">legacy</a> convention, the operating system <a href="Booting" title="Booting">startup</a> drive is still most commonly assigned "C:", however this is not always the case. Since <a href="Personal_computer" title="Personal computer">personal computers</a> now no longer include floppies, and <a href="Optical_disc" title="Optical disc">optical disc</a> and other removable drives typically still start at "D:", letters A and B are available for manual assignment by a user with <a href="System_administrator" title="System administrator">administrative</a> privileges. This assignment will be remembered by the same OS on the same PC next time a removable volume is inserted, as long as there are no conflicts, and as long as the removable drive has not been reformatted on another computer (which changes its <a href="Volume_serial_number" class="mw-redirect" title="Volume serial number">volume serial number</a>), and as long as the OS has not been reinstalled on the computer.

</p><p>On Windows XP, mount points may be managed through the Disk Management snap-in for the Microsoft Management Console. This can be most conveniently accessed through "Computer Management" in the "Administrative Tools" section of the <a href="Control_Panel_(Windows)" title="Control Panel (Windows)">Control Panel</a>.

</p><p>More than one drive letter can refer to a single volume, as when using the <a href="SUBST" title="SUBST">SUBST</a> command.

</p><p><b>Warning:</b> removing drive letters or mount-points for a drive may break some programs, as some files may not be accessible under the known path. For example, if a program is installed at "D:\Program Files\Some Program", it may expect to find its data files at "D:\Program Files\Some Program\Data". If the logical disk previously called "D:" has its drive letter changed to "E:", "Some Program" won't be able to find its data at "D:\Program Files\Some Program\Data", since the drive letter "D:" no longer represents that volume.

</p>

<div class="mw-heading mw-heading3"><h3 id="Unix-like_operating_systems">Unix-like operating systems</h3></div>

<p>In <a href="Unix-like" title="Unix-like">Unix-like</a> operating systems, volumes other than the boot volume have a mount-point somewhere within the filesystem, represented by a path. Logically, the directory tree stored on the volume is grafted in at the mountpoint. By convention, mount-points will often be placed in a directory called '/mnt', though '/media' and other terms are sometimes used.

</p><p>To use a given path as a mount-point for another volume, a directory (sometimes called a "<a href="Directory_(computing)#Folder_metaphor" title="Directory (computing)">folder</a>") must exist there.

</p><p>Unix-like operating systems use the <style data-mw-deduplicate="TemplateStyles:r886049734">

/* start https://en.wikipedia.org/ */

.mw-parser-output .monospaced{font-family:monospace,monospace}

/* end https://en.wikipedia.org/ */

</style><span class="monospaced"><a href="Mount_(computing)" title="Mount (computing)">mount</a></span> command to manipulate mount points for volumes.

</p><p>For example, if a CD-ROM drive containing a text file called 'info.txt' was mounted at '<span class="monospaced">/mnt/iso9660</span>', the text file would be accessible at '<span class="monospaced">/mnt/iso9660/info.txt</span>'.

</p>

<div class="mw-heading mw-heading2"><h2 id="Data_management_speed">Data management speed</h2></div>

<p>Files within a volume can generally be moved to any other place within that volume by manipulating the filesystem, without moving the actual data. However, if a file is to be moved outside the volume, the data itself must be relocated, which is a much more expensive operation.

</p><p>In order to better visualize this concept, one might consider the example of a large library. If a non-fiction work is originally classified as having the subject "plants", but then has to be moved to the subject "flora", one does not need to refile the book, whose position on the shelf would be static, but rather, one needs only to replace the <a href="Index_card" title="Index card">index card</a>. However, to move the book to another library, adjusting index cards alone is insufficient. The entire book must be moved.

</p>

<div class="mw-heading mw-heading2"><h2 id="Labels_and_serial_numbers"> Labels and serial numbers</h2></div>

<p>A <b>volume label</b> is the name given to a specific volume in a filesystem. In the <a href="File_Allocation_Table" title="File Allocation Table">FAT</a> filesystem, the volume label was traditionally restricted to 11 characters (reflecting the <a href="8.3" class="mw-redirect" title="8.3">8.3</a> restrictions, but not divided into name and extension fields) even when <a href="Long_file_name" class="mw-redirect" title="Long file name">long file name</a> was enabled, stored as an entry within a disk's <a href="Root_directory" title="Root directory">root directory</a> with a special volume-label <a href="File_attribute" title="File attribute">attribute</a> bit set, and also copied to an 11-byte field within the Extended <a href="BIOS_Parameter_Block" class="mw-redirect" title="BIOS Parameter Block">BIOS Parameter Block</a> of the disk's boot sector. The label is always stored as <a href="Uppercase" class="mw-redirect" title="Uppercase">uppercase</a> in FAT and <a href="VFAT" class="mw-redirect" title="VFAT">VFAT</a> filesystems, and cannot contain <a href="Special_character" class="mw-redirect" title="Special character">special characters</a> that are also disallowed for regular filenames. In the NTFS filesystem, the length of its volume label is restricted to 32 characters, and can include lowercase characters and even <a href="Unicode" title="Unicode">Unicode</a>. In the <a href="ExFAT" title="ExFAT">exFAT</a> filsystem, the length of its volume label is also restricted to 11 characters, but can include lowercase characters and Unicode. The <span class="monospaced"><a href="Label_(command)" title="Label (command)">label</a></span> command is used to change the label in DOS, Windows, and OS/2. For <a href="GUI" class="mw-redirect" title="GUI">GUI</a> systems like <a href="Windows_Explorer" class="mw-redirect" title="Windows Explorer">Windows Explorer</a>, <style data-mw-deduplicate="TemplateStyles:r1249182868">

/* start https://en.wikipedia.org/ */

.mw-parser-output .keyboard-key{border:1px solid #aaa;border-radius:0.2em;box-shadow:0.1em 0.1em 0.2em rgba(0,0,0,0.1);background-color:var(--background-color-neutral-subtle,#f8f9fa);background-image:linear-gradient(to bottom,var(--background-color-neutral,#eaecf0),var(--background-color-neutral-subtle,#f8f9fa),var(--background-color-neutral,#eaecf0));color:var(--color-base,#202122);padding:0.1em 0.3em;font-family:inherit;font-size:0.85em}

/* end https://en.wikipedia.org/ */

</style><kbd class="keyboard-key nowrap">F2</kbd> can be pressed while the volume is highlighted, or a right-click on the name will bring up a <a href="Context_menu" title="Context menu">context menu</a> that allows it to be renamed, either of which is the same process as for renaming a file. Changing the label in Windows will also change the volume creation <a href="Timestamp" title="Timestamp">timestamp</a> to the current date and time for FAT filesystems. NTFS partitions have the <a href="System_Volume_Information" class="mw-redirect" title="System Volume Information">System Volume Information</a> directory, whose creation timestamp is set when Windows creates the partition, or when it first recognizes a repartitioning (the creation of a new volume) by a separate <a href="Disk_utility" title="Disk utility">disk utility</a>.

</p><p>In contrast to the label, the <b>volume serial number</b> is generally unique and is not normally changed by the user, and thus acts as a more consistent and reliable identifier of when a volume has been changed (as when a disk is removed and another inserted). <a href="Disk_formatting" title="Disk formatting">Disk formatting</a> changes the serial number, but relabeling does not.<sup id="cite_ref-Glass_4-0" class="reference"><a href="#cite_note-Glass-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup> It originated in 1950s in <a href="Mainframe_computer" title="Mainframe computer">mainframe computer</a> operating systems. In <a href="OS/360" class="mw-redirect" title="OS/360">OS/360</a> line it is human-configurable, has a maximum length of six characters, is in uppercase, must start with a letter, and identifies a volume to the system in unique manner. For example, "SYSRES" is often used for a <i>system residence volume</i>. Operating systems may use the volume serial number as mountpoint name.<sup id="cite_ref-5" class="reference"><a href="#cite_note-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup>

</p><p>A <b>volume serial number</b> is a <a href="Serial_number" title="Serial number">serial number</a> assigned to a <a href="Disk_storage" title="Disk storage">disk volume</a> or <a href="Magnetic_tape_data_storage" class="mw-redirect" title="Magnetic tape data storage">tape volume</a>.

In <a href="File_Allocation_Table" title="File Allocation Table">FAT</a> and <a href="NTFS" title="NTFS">NTFS</a> <a href="File_system" title="File system">file systems</a>, a <b>volume serial number</b> is a feature used to determine if a <a href="Disk_storage" title="Disk storage">disk</a> is present in a drive or not, and to detect if it was exchanged with another one. This identification system was created

by <a href="Microsoft" title="Microsoft">Microsoft</a> and <a href="International_Business_Machines" class="mw-redirect" title="International Business Machines">IBM</a> during their development of <a href="OS/2" title="OS/2">OS/2</a>.<sup id="cite_ref-Letwin_6-0" class="reference"><a href="#cite_note-Letwin-6"><span class="cite-bracket">[</span>6<span class="cite-bracket">]</span></a></sup> It was introduced in <a href="MS-DOS_4.01" class="mw-redirect" title="MS-DOS 4.01">MS-DOS 4.01</a> in 1988.

</p><p>The volume serial number is a 32-bit number determined by the date and time on the real-time clock on the current computer at the time of a disk's <a href="Disk_formatting" title="Disk formatting">formatting</a>. Previously, determination by the OS of whether a disk was swapped was done by reading the drive's <i>volume label</i>. However, even at that time the volume label was not required to be unique and was optional. Therefore, many users had not given disks any meaningful name and the old method failed.

</p><p>The <span class="monospaced"><a href="Vol_(command)" title="Vol (command)">vol</a></span> command can be used from the <a href="Command_line" class="mw-redirect" title="Command line">command line</a> to display the current label and serial number of a volume.

</p>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://msdn.microsoft.com/en-us/library/dd163557.aspx">"Understanding Disk Terminology"</a>. Microsoft Corporation<span class="reference-accessdate">. Retrieved <span class="nowrap">2014-06-10</span></span>. <q>Partition A portion of the hard disk. In many cases, this is the entire hard disk space, but it needn't be. Volume A unit of disk space composed of one or more sections of one or more disks. Prior versions of Windows Server used volume only when referring to dynamic disks, but Windows Server 2008 uses it to mean partitions as well.</q></cite></span>

</li>

<cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://msdn.microsoft.com/en-us/library/dd163559.aspx">"Partitions and Volumes"</a>. Microsoft Corporation<span class="reference-accessdate">. Retrieved <span class="nowrap">2014-06-10</span></span>. <q>In Windows Server 2008 the distinction between volumes and partitions is somewhat murky. When using Disk Management, a regular partition on a basic disk is called a simple volume, even though technically a simple volume requires that the disk be a dynamic disk.</q></cite></span>

</li>

<cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://technet.microsoft.com/en-us/magazine/dd637755.aspx">"Use Built-In Tools to Create Partitions and Volumes in Windows Server"</a>. Microsoft Corporation. 2008-06-18<span class="reference-accessdate">. Retrieved <span class="nowrap">2014-06-10</span></span>. <q>Windows Server 2008 simplifies the Disk Management user interface by using one set of dialog boxes and wizards for both partitions and volumes.</q></cite></span>

</li>

<li id="cite_note-Glass-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-Glass_4-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFGlass1998" class="citation web cs1">Glass, Brett (1998-02-06). <a rel="nofollow" class="external text" href="http://www.brettglass.com/ttr19980206a.html">"Changing a Disk's Volume Serial Number"</a>. <i>Brett Glass To The Rescue</i><span class="reference-accessdate">. Retrieved <span class="nowrap">2006-07-28</span></span>.</cite></span>

</li>

<li id="cite_note-5"><span class="mw-cite-backlink"><b><a href="#cite_ref-5">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://bitbucket.org/zxtune/zxtune/issues/140/issue-with-xpsf-playlists">"Issue with .XPSF playlists"</a>.</cite></span>

</li>

<cite id="CITEREFLetwin1988" class="citation book cs1"><a href="Gordon_Letwin" title="Gordon Letwin">Letwin, Gordon</a> (1988). <span class="id-lock-registration" title="Free registration required"><a rel="nofollow" class="external text" href="https://archive.org/details/insideos200letw"><i>Inside OS/2</i></a></span>. <a href="Microsoft_Press" title="Microsoft Press">Microsoft Press</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>1-55615-117-9</bdi>.</cite></span>

</li>

</ol></div></div>

<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>

<ul><li>MSDN's article on <a rel="nofollow" class="external text" href="http://msdn.microsoft.com/en-us/library/aa365006.aspx">Hard Links and Junctions</a></li></ul></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-08-08" href="https://en.wikipedia.org/wiki/?title=Volume_(computing)&oldid=1304804740">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>